<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Help - The Sprint Review Page</title>
    <link rel="stylesheet" href="Style.css" />
</head>

<body>
    <a href="Default_help.htm">
    <img border="0" src="../Images/Banner2_Web.png" />
    </a>
    <br /><br />
    
    <p class="header1">Sprint Review Page</p>
    <p>This page generates a document that contains the sprint backlog, sprint burn down graph and sprint retrospective notes. This document can be exported in Excel or PDF format.</p>
    <hr />
    
    <p class="header1">Document Description - The Sprint Backlog</p>
    <img src="images/sprint_review_1.jpg" />
    <ul>
       <li>The first part of the sprint review document is a copy of the products, features and tasks worked on during the sprint. This is generated from the sprint backlog and is sorted by product and then by feature and then by task priority, excepted in discovered work where it is sorted by the task name instead of priority. It contains the following:
            <ul type="circle">
            <li><font class="header3">Product</font> - This column includes the name of the product the feature and tasks are associated with.</li>
            <li><font class="header3">Feature - Tasks</font> - This column includes the name of the feature in the green row, with each individual task related to the feature in the white rows below it.</li>
            <li><font class="header3">Base</font> - This column includes the number of hours/days initially estimated for completing all the tasks related to this feature during the selected sprint.</li>
            <li><font class="header3">Actual</font> - This column includes the actual number of hours/days that were spent working on tasks related to this feature during the selected sprint.</li>
            <li><font class="header3">Punted</font> - This column includes the number of hours/days remaining to complete the tasks related to this feature. These hours/days have been punted and must be completed in a future sprint.</li>
            </ul>
       </li> 
    </ul>
    
    <hr />
    
    <p class="header1">Document Description - The Sprint Totals Table</p>
    <img src="images/sprint_review_2.jpg" />
    <ul>
         <li>To move to the second part of the sprint review document, click the right arrow at the top of the document.</li> 
         <li>The second part of the sprint review document is a copy of the burndown graph which shows the scrum team's progress throughout the sprint, as described below:
            <ul type="circle">
            <li><font class="header3">Name</font> - This column includes the alias of the team member.</li>
            <li><font class="header3">Buffer</font> - This column includes a numberic value indicating the estimated buffer of the team member which was set at the beginning of the sprint. The buffer indicates how much how a team member is able to accomplish during a standard 8 hour work day. A buffer of greater than 1 means that the team member is getting less than 8 hours of work done per day, while a buffer less than 1 means the team member is getting more than 8 hours of work accomplished.</li>
            <li><font class="header3">OOF Time</font> - This column includes a numeric value indicating the amount of time the team member estimated to spend OOF during the sprint.</li>
            <li><font class="header3">Available Time</font> - This column includes a numeric value indicating the amount of time the team member has to complete work. This takes into account OOF hours/days, unbuffered tasks and the team member's estimated buffer. </li>
            <li><font class="header3">Base Work</font> - This column includes a numeric value indicating the initial estimation of time for all the tasks assigned to this team member during the sprint. It is displayed in either hours or days, based on the user's selection above.</li>
            <li><font class="header3">Over Allocated</font> - This column includes a numeric value indicating the amount of time the base work value is over or under the amount of available time for that team member during the currently selected sprint. A negative value indicates the team member is under allocated, while a positive value indicates the team member is over allocated.</li>
            <li><font class="header3">Work Completed</font> - This column includes a numeric value indicating the amount of work the team member has completed during the currently selected sprint. </li>
            <li><font class="header3">Work Remaining</font> - This column includes a numeric value indicating the amount of work the team member still has to complete during the currently selected sprint.</li>
            <li><font class="header3">OOF Remaining</font> - This column includes a numeric value indicating the amount of OOF time the team member still has to take during the currently selected sprint.</li>
            <li><font class="header3">Ahead Behind</font> - This column includes a numeric value indiciating the amount of time the team member is ahead or behind schedule during the currently selected sprint. A positive value indicates the team member is ahead, while a negative value indicates the user is behind.</li>
            <li><font class="header3">Work Punted</font> - This column includes a numeric value indicating the amount of work the team member has punted during the currently selected sprint. This is work that must be completed in a future sprint.</li>
            <li><font class="header3">Actual OOF</font> - This column includes a numeric value indicating the amount of time the team member has actually spent OOF during the currently selected sprint.</li>
            <li><font class="header3">Planned Work</font> - This column includes a numeric value indicating the amount of time the team member has spent doing work that was planned to be completed at the start of the sprint.</li>
            <li><font class="header3">Discovered Work</font> - This column includes a numeric value indicating the amount of time the team member has spent doing work that was not scheduled to be completed at the start of the sprint.</li>
            <li><font class="header3">Punted vs. Discovered Buffer</font> - This column includes a numeric value indicating the ratio of time spent by the team member doing work that was planned at the start of the work and work that was discovered during the course of the sprint.</li>
            <li><font class="header3">Work Buffer</font> - This column includes a numeric value indicating the current buffer for the team member, taking into account OOF time, unbuffered tasks and buffered tasks. The buffer indicates how much how a team member is able to accomplish during a standard 8 hour work day. A buffer of greater than 1 means that the team member is getting less than 8 hours of work done per day, while a buffer less than 1 means the team member is getting more than 8 hours of work accomplished.</li>
            </ul>
       </li> 
    </ul>
    
    <hr />
    
    <p class="header1">Document Description - The Burn Down Graph</p>
    <img src="images/burndown_1.jpg" />
    <ul>
       <li>To move to the second part of the sprint review document, click the right arrow at the top of the document.</li> 
       <li>The second part of the sprint review document is a copy of the burndown graph which shows the scrum team's progress throughout the sprint, as described below:
            <ul type="circle">
            <li><font class="header3">Scheduled</font> - This line of the graph represents the number of hours/days of work the team has scheduled for the currently selected sprint. This number will increase as work is discovered and decrease as work is punted.</li>
            <li><font class="header3">Actual</font> - This line on the graph tracks the number of hours/days the team members have completed on planned and discovered work during the currently selected spring. This line should meet the scheduled line by the end of the sprint.</li>
            <li><font class="header3">Remaining</font> - This line on the graph tracks how many hours/days the team members have remaining in order to complete all planned and discovered work for the currently selected sprint. This line will decrease as work is completed or punted, and will increase as work is discovered.</li>
            <li><font class="header3">Punted</font> - This line on the graph tracks how many hours/days of work the team members are punting, in order to complete them in a future sprint. This line should remain as close to zero as possible.</li>
            <li><font class="header3">Discovered</font> - This line on the graph tracks how many hours/days the team members are spending on work that was not planned at the start of the currently selected sprint. This line should remain as close to zero as possible.</li>
            <li><font class="header3">Trend Remaining</font> - This line on the graph is a prediction of where the team will end up based on the work already completed, work remaining and work punted.</li>
            <li><font class="header3">X Axix - Days in Sprint</font> - The values on the X axis represent the days that are included in the currently selected sprint.</li>
            <li><font class="header3">Y Axis - Work Days</font> - The values on the Y axis represent work days. A work day is one team member completing 8 hours of work.</li>
            </ul>
       </li> 
    </ul>
    
    <hr />
    
     <p class="header1">Document Description - The Sprint Retrospective Notes</p>
     <img src="images/sprint_review_3.jpg" />
     <ul>
       <li>To move to the third part of the sprint review document, click the right arrow at the top of the document.</li>  
       <li>The third part of the sprint review document is a copy of the sprint retrospective notes, entered at the end of the sprint, as described below:
            <ul type="circle">
            <li><font class="header3">Sprint Positives</font> - This field includes a list of all the positive things that happened during the sprint. This can include task related items, team related items, or anything else that has been specified by the team's scrum master.</li>
            <li><font class="header3">Sprint Negatives</font> - This field includes a list of all the negative things that happened during the sprint. This can include task related items, team related items, or anything else that has been specified by the team's scrum master.</li> 
            <li><font class="header3">Changes For Next Sprint</font> - This field includes a a list of all the things the team should consider changing for the next sprint in order to make the next sprint more productive. This can include task related items, team related items, or anything else that has been specified by the team's scrum master.</li>
            </ul>
       </li> 
    </ul>
    
    <hr />
    
    <p class="header1">Creating and Exporting the Sprint Review Document</p>
    <img src="images/export_1.jpg" />
     <ol>
       <li>Select the sprint whose review you want to generate from the dropdown list at the top of the page.</li> 
       <li>Review the information in the document to make sure it looks correct.</li>
       <li>At the top of the document select a format in the "Select a Format" dropdown.</li>
       <li>Click the "Export" link.</li>
       <li>A new internet explorer window will open and a dialog box will appear allowing you to decide whether to open or save the document.</li>
    </ol>
    

</body>
</html>
